-- *****************************************************************
-- CISCO-STUN-MIB.my: Cisco STUN MIB
--
-- April 1995, Bob Clouston
--
-- Copyright (c) 1995 by cisco Systems, Inc.
-- All rights reserved.
-- *****************************************************************
--CISCO-STUN-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,NOTIFICATION-TYPE,Counter32,IpAddressFROM SNMPv2-SMI
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF
ifIndex,InterfaceIndexFROM IF-MIB
TruthValueFROM SNMPv2-TC
ciscoMgmt
FROM CISCO-SMI;ciscoStunMIB MODULE-IDENTITYLAST-UPDATED"9508210000Z"ORGANIZATION"Cisco Systems, Inc."CONTACT-INFO" Cisco Systems
Customer Service
Postal: 170 W. Tasman Drive
San Jose, CA 95134
USA
Tel: +1 800 553-NETS
e-mail: cs-snmp@cisco.com"DESCRIPTION"The MIB module for serial Tunneling.
Overview of STUN MIB
MIB description
The STUN MIB provides the configuration and operational information
on Cisco's serial tunnelling implementation. The following entities
are managed:
1) Global STUN information
2) STUN groups
3) STUN ports
4) STUN routes
The following example configuration shows how the STUN MIB returns
STUN information, from either CISCO A or CISCO B.
HOST == SDLC == Cisco A == IP Network == Cisco B == SDLC == SDLC
line line device
1) The STUN global entry identifies the IP address by which the
router is known to other STUN peers.
2) The STUN group table identifies the STUN group number and protocol
type that Cisco A and Cisco B use to route SDLC traffic over the
IP network. The table contains an entry for each STUN group
defined on the router.
3) The STUN port table identifies the serial interface to the SDLC
line for which the router is doing serial tunnelling. The MIB also
identifies the STUN group this interface is defined for, and
identifies the default routing for unrecognized SDLC addresses.
There is a port entry for each STUN-enabled interface on the router.
4) The STUN route table has an entry for each address defined for
routing within the STUN group, and an entry for the default routing
if the 'stun route all' command is configured. The route entry
includes identification of the STUN peer, priority, state, whether
local acknowledgment is enabled, and packet and byte counters.
"REVISION"9508210000Z"DESCRIPTION"Added revision clause, formatting cleanup."REVISION"9503170000Z"
DESCRIPTION"Initial version of this MIB module."::={ ciscoMgmt 30}stunObjects OBJECTIDENTIFIER::={ ciscoStunMIB 1}stunGlobal OBJECTIDENTIFIER::={ stunObjects 1}stunGroups OBJECTIDENTIFIER::={ stunObjects 2}stunPorts OBJECTIDENTIFIER::={ stunObjects 3}stunRoutes OBJECTIDENTIFIER::={ stunObjects 4}-- ******************************************************************
-- * global values for router
-- ******************************************************************stunIPAddr OBJECT-TYPESYNTAXIpAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The configured IP address used for all serial tunnelling
in this router."::={ stunGlobal 1}-- ******************************************************************
-- * stun Group Table
-- ******************************************************************stunGroupTable OBJECT-TYPESYNTAXSEQUENCEOF StunGroupEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table of entries representing STUN groups configured on the
router. Each STUN-enabled interface is assigned to a STUN
group, and packets can only travel between STUN-enabled
interfaces in the same group."::={ stunGroups 1}stunGroupEntry OBJECT-TYPESYNTAX StunGroupEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Status and parameter values for a group."INDEX{ stunGroupIndex }::={ stunGroupTable 1}
StunGroupEntry ::=SEQUENCE{
stunGroupIndex
INTEGER,
stunProtocolType
INTEGER}stunGroupIndex OBJECT-TYPESYNTAXINTEGER(1..255)MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"The configured STUN group number."::={ stunGroupEntry 1}stunProtocolType OBJECT-TYPESYNTAXINTEGER{basic(1),-- non-SDLC, such as HDLCsdlc(2),-- SDLC protocolsdlctg(3),-- SNA transmission groupcustom(4)-- customer-defined protocol}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The protocol type for this STUN group."::={ stunGroupEntry 2}-- ******************************************************************
-- * stun Port Table
-- ******************************************************************stunPortTable OBJECT-TYPESYNTAXSEQUENCEOF StunPortEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A list of STUN-enabled interfaces (ports)."::={ stunPorts 1}
stunPortEntry OBJECT-TYPESYNTAX StunPortEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Status and parameter values for a STUN port."INDEX{ ifIndex }::={ stunPortTable 1}
StunPortEntry ::=SEQUENCE{
stunPortGroupIndex
INTEGER,
stunPortDefaultPeerType
INTEGER,
stunPortDefaultPeerIP
IpAddress,
stunPortDefaultPeerSerialInterface
InterfaceIndex}stunPortGroupIndex OBJECT-TYPESYNTAXINTEGER(1..255)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The group number to which the stun port
belongs. Frames will only be routed to other
ports (on this or another router) in the same
stun group. This group must match a stunGroupIndex
in the stunGroupTable."::={ stunPortEntry 1}stunPortDefaultPeerType OBJECT-TYPESYNTAXINTEGER{other(1),ip(2),direct(3),frameRelay(4)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The type of identification of the default partner
for unrecognized addresses. If there
is no default route then the stunRouteType
field of stunPortDefaultRemote is 'other'.
If ip then the value is in stunRouteIP; if serial or
serialDirect then the value is in stunRouteSerial."::={ stunPortEntry 2}stunPortDefaultPeerIP OBJECT-TYPESYNTAXIpAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The ip address of the remote default STUN partner,
for unrecognized addresses.
0.0.0.0 is returned if the default route type is not ip."::={ stunPortEntry 3}stunPortDefaultPeerSerialInterface OBJECT-TYPESYNTAXInterfaceIndexMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"If stunRouteType is serial then this is the
serial interface index of the point-to-point
link to the remote partner;
if stunRouteType is serialDirect then the
partner is in the local STUN.
if stunRouteType is ip then this field is
0."::={ stunPortEntry 4}-- ******************************************************************
-- * Route Table
-- ******************************************************************stunRouteTable OBJECT-TYPESYNTAXSEQUENCEOF StunRouteEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table containing information about specific SDLC
addresses. There is one table entry for each SDLC
address configured by the STUN ROUTE command."::={ stunRoutes 1}stunRouteEntry OBJECT-TYPESYNTAX StunRouteEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The information regarding a single STUN address."INDEX{ stunGroupIndex, stunRouteStationAddress }::={ stunRouteTable 1}
StunRouteEntry ::=SEQUENCE{
stunRouteStationAddress
INTEGER,
stunRouteType
INTEGER,
stunRouteRemoteIP
IpAddress,
stunRouteSerialInterface
InterfaceIndex,
stunRoutePriority
INTEGER,
stunRoutePeerState
INTEGER,
stunRouteLocalAck
TruthValue,
stunRouteRxPackets
Counter32,
stunRouteTxPackets
Counter32,
stunRouteRxBytes
Counter32,
stunRouteTxBytes
Counter32}stunRouteStationAddress OBJECT-TYPESYNTAXINTEGER(1..256)MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The poll address of the station. 256 indicates the ALL parameter
on the STUN ROUTE command, which is the route for all
unrecognized addresses."::={ stunRouteEntry 1}stunRouteType OBJECT-TYPESYNTAXINTEGER{other(1),ip(2),direct(3),frameRelay(4)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The type of identification of the remote partner."::={ stunRouteEntry 2}stunRouteRemoteIP OBJECT-TYPESYNTAXIpAddressMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The ip address of the remote STUN partner.
0.0.0.0 if partner type is not ip."::={ stunRouteEntry 3}stunRouteSerialInterface OBJECT-TYPESYNTAXInterfaceIndexMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The local interface index to the remote partner.
0 is returned if the partner type is not direct or frameRelay."::={ stunRouteEntry 4}stunRoutePriority OBJECT-TYPESYNTAXINTEGER{low(1),normal(2),medium(3),high(4)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The priority with which this station's traffic will
be routed across the network."::={ stunRouteEntry 5}stunRoutePeerState OBJECT-TYPESYNTAXINTEGER{dead(1),closed(2),opening(3),openWait(4),connected(5),direct(6)}MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The state of the peer connection through the
STUN tunnel."::={ stunRouteEntry 6}stunRouteLocalAck OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-only
STATUScurrentDESCRIPTION"Indicates if the STUN connection is locally acknowledged.
TRUE-> STUN connection is locally acknowledged
FALSE-> STUN connection is not locally acknowledged
"::={ stunRouteEntry 7}stunRouteRxPackets OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of frames received from the serial
interface with this station's address."::={ stunRouteEntry 8}stunRouteTxPackets OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of frames transmitted at the serial
interface with this station's address."::={ stunRouteEntry 9}stunRouteRxBytes OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of bytes received from the serial
interface with this station's address."::={ stunRouteEntry 10}
stunRouteTxBytes OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Count of bytes transmitted at the serial
interface with this station's address."::={ stunRouteEntry 11}-- *************************************************************************
-- * STUN notifications
-- *************************************************************************stunNotificationPrefix OBJECTIDENTIFIER::={ ciscoStunMIB 2}stunNotifications OBJECTIDENTIFIER::={ stunNotificationPrefix 0}stunPeerStateChangeNotification NOTIFICATION-TYPEOBJECTS{ stunRoutePeerState }STATUScurrentDESCRIPTION"This notification indicates that the state of a STUN route
has transitioned to active (connected or direct) or inactive
(dead or closed)."::={ stunNotifications 1}-- *************************************************************************
-- * Conformance Information
-- *************************************************************************
--stunMibConformance OBJECTIDENTIFIER::={ ciscoStunMIB 3}stunMibCompliances OBJECTIDENTIFIER::={ stunMibConformance 1}stunMibGroups OBJECTIDENTIFIER::={ stunMibConformance 2}--
-- *************************************************************************
-- * Compliance Statements
-- *************************************************************************stunMibCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for STUN."MODULE-- this moduleMANDATORY-GROUPS{
stunGlobalGroup,
stunGroupGroup,
stunPortGroup,
stunRouteGroup
}::={ stunMibCompliances 1}stunGlobalGroup OBJECT-GROUPOBJECTS{
stunIPAddr
}STATUScurrentDESCRIPTION"A collection of objects providing global STUN information."
::={ stunMibGroups 1}stunGroupGroup OBJECT-GROUPOBJECTS{
stunProtocolType
}STATUScurrentDESCRIPTION"A collection of objects providing information about
STUN groups ."::={ stunMibGroups 2}stunPortGroup OBJECT-GROUPOBJECTS{
stunPortGroupIndex,
stunPortDefaultPeerType,
stunPortDefaultPeerIP,
stunPortDefaultPeerSerialInterface
}STATUScurrentDESCRIPTION"A collection of objects providing information about
STUN enabled interfaces."::={ stunMibGroups 3}stunRouteGroup OBJECT-GROUPOBJECTS{
stunRouteType,
stunRouteRemoteIP,
stunRouteSerialInterface,
stunRoutePriority,
stunRoutePeerState,
stunRouteLocalAck,
stunRouteRxPackets,
stunRouteTxPackets,
stunRouteRxBytes,
stunRouteTxBytes
}STATUScurrentDESCRIPTION"A collection of objects providing information about
STUN defined routes."::={ stunMibGroups 4}END